Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0890

reference: 405-tree-1
name: 0890
tree-preservation-order: undefined
405-tpo-1
uprn
address-text
point: POINT (-1.025956 50.890073)
geometry: MULTIPOLYGON (((-1.025928 50.890070,-1.025929 50.890075,-1.025933 50.890080,-1.025939 50.890084,-1.025947 50.890087,-1.025956 50.890088,-1.025973 50.890085,-1.025979 50.890081,-1.025983 50.890076,-1.025985 50.890070,-1.025980 50.890060,-1.025965 50.890053,-1.025957 50.890052,-1.025940 50.890055,-1.025929 50.890064,-1.025928 50.890070)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL